D110P 大概半小时或1小时左右链路断线

[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Bad FCS ( on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Bad FCS ( on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Bad FCS ( on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Bad FCS ( on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Bad FCS ( on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Bad FCS ( on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Bad FCS ( on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Bad FCS ( on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Bad FCS ( on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Bad FCS ( on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Jun 8 02:05:12] NOTICE[2758] chan_dahdi.c: PRI got event: HDLC Bad FCS

[Jun 8 16:28:09] VERBOSE[2758] logger.c: == Primary D-Channel on span 1 up
[Jun 8 16:28:09] ERROR[2758] chan_dahdi.c: ACK received for '1' outside of window of '0' to '0', restarting
[Jun 8 16:28:09] VERBOSE[2758] logger.c: == Primary D-Channel on span 1 down
[Jun 8 16:28:09] WARNING[2758] chan_dahdi.c: No D-channels available! Using Primary channel 16 as D-channel anyway!
[Jun 8 16:28:09] VERBOSE[2758] logger.c: == Primary D-Channel on span 1 up
[Jun 8 16:28:09] VERBOSE[2758] logger.c: -- B-channel 0/31 restarted on span 1
[Jun 8 16:28:09] VERBOSE[2758] logger.c: -- B-channel 0/25 restarted on span 1
[Jun 8 16:28:09] VERBOSE[2758] logger.c: -- B-channel 0/24 restarted on span 1
[

Hi, "[Jun 7 17:47:04] ERROR[2758] chan_dahdi.c: !! Got S-frame while link down" 这个错误似乎是数据包延时或者不同步引起的，这可能与你的时钟设置有关系，你的/etc/dahdi/system.conf里面的span参数是什么？

i] Last edited by Joe.Yung at 2010-6-7 16:10 [/i

# Autogenerated by /usr/local/sbin/genzaptelconf -- do not hand edit
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#

# It must be in the module loading order


# Span 1: WCT1/0 "Digium Wildcard TE110P T1/E1 Card 0"
# channel 1, WCT1, unhandled for now
# channel 2, WCT1, unhandled for now
# channel 3, WCT1, unhandled for now
# channel 4, WCT1, unhandled for now
# channel 5, WCT1, unhandled for now
# channel 6, WCT1, unhandled for now
# channel 7, WCT1, unhandled for now
# channel 8, WCT1, unhandled for now
# channel 9, WCT1, unhandled for now
# channel 10, WCT1, unhandled for now
# channel 11, WCT1, unhandled for now
# channel 12, WCT1, unhandled for now
# channel 13, WCT1, unhandled for now
# channel 14, WCT1, unhandled for now
# channel 15, WCT1, unhandled for now
# channel 16, WCT1, unhandled for now
# channel 17, WCT1, unhandled for now
# channel 18, WCT1, unhandled for now
# channel 19, WCT1, unhandled for now
# channel 20, WCT1, unhandled for now
# channel 21, WCT1, unhandled for now
# channel 22, WCT1, unhandled for now
# channel 23, WCT1, unhandled for now
# channel 24, WCT1, unhandled for now
# channel 25, WCT1, unhandled for now
# channel 26, WCT1, unhandled for now
# channel 27, WCT1, unhandled for now
# channel 28, WCT1, unhandled for now
# channel 29, WCT1, unhandled for now
# channel 30, WCT1, unhandled for now
# channel 31, WCT1, unhandled for now

# Span 2: ZTDUMMY/1 "ZTDUMMY/1 1"

# Global data

span=1,1,0,ccs,hdb3,crc4
bchan=1-15
dchan=16
bchan=17-31

loadzone = us
defaultzone = us

之前这个配置在另外一台机子上一直正常工作的呀，现在是客户换了一台服务器，把原来的配置放上来就出现这种现象了，原来和现在的系统都是ASTERISKNOW

;
; Zapata telephony interface
;
; Configuration file

[trunkgroups]

[channels]

language=en
context=from-pstn
switchtype = national
overlapdial = yes
signalling = pri_cpe
group = 1
channel => 1-15
channel => 17-31

callerid=asreceived
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=400
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
busydetect=yes
busycount=6
callprogress=yes
faxdetect=incoming

;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no

;Include genzaptelconf configs
#include zapata-auto.conf

;group=1

;Include AMP configs
#include zapata_additional.conf